Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1809

reference: 276-tree-1
name: 1809
tree-preservation-order: undefined
276-tpo-1
uprn
address-text
point: POINT (-0.979087 50.859058)
geometry: MULTIPOLYGON (((-0.978988 50.859048,-0.978993 50.859067,-0.979006 50.859085,-0.979028 50.859099,-0.979056 50.859108,-0.979086 50.859111,-0.979117 50.859109,-0.979145 50.859100,-0.979167 50.859086,-0.979182 50.859069,-0.979187 50.859049,-0.979183 50.859030,-0.979169 50.859012,-0.979147 50.858998,-0.979120 50.858989,-0.979089 50.858986,-0.979058 50.858988,-0.979030 50.858997,-0.979008 50.859011,-0.978993 50.859028,-0.978988 50.859048)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL